Subject: To IETF or not to IETF

From: David Bryant/HQ/3Com <David_Bryant/HQ/[email-masked]>
Date: 4 May 94 18:34:46 PS

3Com Corp is in favor of option 2:  Develop the DLSw in the AIW and deliver it 
to the IETF as an          informational RFC. 

The reasons are as follows:

1.  The industry perception of IETF "RFCs" (both informational and standard 
specifications)
 is deemed a positive stamp of approval.  Therefore, there is value to IETF RFC 
status
 and option 1 (AIW only) is not desirable.

2. Option 3 (IETF after AIW closed pages) is not viable as this may result in 
multiple DLSw 
  specifications which are not the same at worst.  And at best it delays the 
standardization
  process due to serialization.

3. Option 2 is quicker than option 4.   This is clearly true for several 
reasons.  The IETF 
 process has not yet begun and it has a number of stages just as the AIW 
does.     The   IETF requires two interoperable implementations based upon the 
specification, the AIW   does not.  

4.  From our perspective the vast majority of the industry does not make a 
distinction    between informational RFCs and IETF standard RFCs.   Thus an 
informational RFC   seems to accomplish the goal of industry acceptance 
associated with IETF RFCs.   

5. What is truly critical is that the DLSw specification (AIW or IETF 
standard), be written to 
   facilitate consistent  interoperable implementations amongst multiple 
vendors which   provide a valuable network solution to our customers.  This can 
be accomplished in 
 either the AIW or the IETF assuming we do not grant "standard" or "CP" status 
in a 
  frivolous manner.  So in this sense, the IETF standard is not required.

6.  Interactive participation from the IETF will require additional effort that 
does not seem 
 business case justified.  If not simply attending more meetings, clearly 
following more  
 activity on the internet.

7. Pursuit of an IETF standard will only prolong the standardization of DLSw    
(as noted in bullet 3), which will further thwart AIW member attempts to     
develop a marketable SNA/NetBios TCP/IP encapsulation technique thus maintaining
 the marketplace status quo.  

David Bryant